add Alias field to backends, support at CLI and store levels #150
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
#147 made a couple of breaking changes to the CLI:
python-python2-poetry
backendpython-python3-poetry
backend name topython3-poetry
unfortunately, the latter change will cause all upm caches to be invalidated, and invocations of
upm -l python-python3-poetry
will break.What changed
Alias
field toapi.LanguageBackend
-l
flag, if resolving viaName
of theLanguageBackend
fails, try to resolve against theAlias
Name
, if there is then use that cacheAlias
, if there is then use that cacheName
, exit function if trueAlias
, exit function if trueName